home *** CD-ROM | disk | FTP | other *** search
- Date: Fri, 29 Jul 94 23:33 CDT
- From: ekl@sdf.lonestar.org (Evan K. Langlois)
- To: gem-list@world.std.com
- Subject: Re: Amodal Dialogs
- Precedence: bulk
-
- ========================================================================
- Everything would be just dandy if something weren't preventing these
- WM_TOPPED messages from being sent. Other messages seem to get sent just
- fine, and the problem clears up if I click anywhere outside of the window
- in question... until I press a button again.
- ========================================================================
-
- Its a bug in the AES. I get it too. Sometimes, I just get clicks with
- background windows instead of a top. I get it in TOSWIN alot, which is
- when I have lots of windows open, so that could be part of it. I just
- jam the mouse into the menu bar and then click (since I usually have
- window everywhere, and the menu bar is the only place uncovered!)
-
- Your solution .. you said you were simulating mouse events. How did
- you do this. I wanna see how much it changes the code I posted previously.
- Since the code I posted allowed some pretty radical behavior (the use
- of the other mouse buttons during a drag!) and I don't want to lose
- that flexibility. In fact, I don't want to call any graf_ functions
- or anything else that creates a mode. I want to flow everything though
- evnt_multi() with an optimized binding (no stack usage, etc) and doll
- out the events to other objects from there.
-
-